home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 19
/
Night Owl (The Best of Shareware)(NOPV 19)(1996).ISO
/
018a
/
elrul512.zip
/
PKEYDROP.RUL
< prev
next >
Wrap
Text File
|
1995-05-31
|
6KB
|
155 lines
--- Following message extracted from PKEY_DROP @ 1:374/14 ---
By Christopher Baker on Wed May 31 20:40:26 1995
From: Christopher Baker
To: All
Date: 17 May 95 18:28:50
Subj: PKEY_DROP Echo Guidelines - regular repost
-----BEGIN PGP SIGNED MESSAGE-----
This is the PKEY_DROP Echo. The purpose of the Echo is to provide a place
to post and find public-keys for data privacy and electronic signatures
within FidoNet.
This is a companion conference to PUBLIC_KEYS Echo. It is distributed via
the same channels as PUBLIC_KEYS. It is not intended for general message
traffic but questions relating to public-key problems and bogus key notices
are permitted. Simply identify and drop your personal public-key into this
Echo and conduct any general discussion in PUBLIC_KEYS Echo. Keyrings are
NOT permitted to be posted here. Please do not post keyserver reports
here. Multiple personal keys are permitted.
This is a technical Echo with very few rules. Those very few rules are:
1. Stay on-topic. Public-key posts are the main purpose and notice of
key problems or bogus keys is the secondary purpose.
2. ONLY personal public-keys are to be posted here. Keyrings MAY NOT
be entered into the Echo. If anyone wants a keyring, they can go
file-request one from an appropriate source.
3. No Private flagged messages in Echomail! Encrypted traffic as
public-keys is permitted because that is what this Echo is for.
User-specific encrypted traffic is not permitted since it defeats
the purpose of Echomail.
4. Clear-signing a key post adds an additional layer of processing and
is not necessary. Please consider your audience when deciding to
clear-sign a key post.
5. Be aware that Echomail is NOT secure. Don't take anything at face value.
6. The posts in this Echo are the sole responsiblity of the poster. If you
need verification, use Netmail.
7. The Moderators will deal with off-topic traffic. Don't respond for them.
Links to this Echo will only be curtailed when absolutely necessary so
please don't make it necessary. [grin]
The Moderators are Christopher Baker [KeyID: 1024/F89A24F9 1994/05/18]
and GK Pace [KeyID: 1024/EE38FB41 1994/05/14] at 1:374/14 and 1:374/26,
respectively.
This Echo is Gated into Zone 2 by Jens Mueller at 2:24/24 who sends it on
to Harry Bush at 2:51/2. Consult either Jens or Harry for Zone 2 feeds. The
Echo is gated into Zone 3 by Jackson Harding at 3:800/857. [thanks, guys!]
The other Zones are open [hint, hint].
KEYNOTES:
ONE-
If you have generated a public-key of 1024 bits with 2.3a or later
versions of PGP, you probably don't need to revoke the old one and make
a new one. This is particularly true if your key was made with any of
the 2.6 generations. If you're worried about getting 2.6.2 or later on
your key, don't make a new one, just re-export your public-key with the
newer version of PGP using the standard key export command:
PGP -kxa youruserid youruserfilename
and then copy the new copy of your public-key to your file directory so
people can file-request or download it.
TWO-
MAKE SURE you distribute the PUBLIC-KEY ONLY! Every so often a neophyte
will put his/her secret-key into circulation. That's BAD!
THREE-
When making your first public-key pair or a new public-key pair, go for
the 1024 bit size. Don't make your key any more vulnerable than you need
to regardless of how long it takes to compile it. If you go for the 2K
size key, keep in mind that 2047 bits is NORMAL.
FOUR-
MAKE SURE you put all your possible userids on your public-key after you
generate it and before you circulate it for use and/or signatures. It is
especially important to be sure that your standard User Name is on there
EXACTLY as it appears in the From: line on your Netmail and Echomail.
This makes it much simpler for folks to encrypt to your name as detected
in a reply.
It also makes life simpler if your Netmail name, your public-key name
and your FidoNet Nodelisting name are all the SAME name!
FIVE-
It is recommended that individual, public-keys be made available via Netmail
or by file-request with the magic filename: PGPKEY and that the public-key
provided for that request by given a distinctive filename using part or all
of each provider's name and address. For example, on my system, a
file-request of PGPKEY will give BAK37414.ASC to the requesting system. A
magic filename of KEYRING will yield extracts from my Public Keyring as
BAKPUB14.ASC. This will avoid duplicate overwriting and make it easier to
track the keys. Using standard magic filenames will make it easier to find
keys and keyrings on different systems.
SIX-
DO NOT SIGN someone's public-key UNLESS you have obtained it directly
from them or their system under password or by direct file-request.
Signing the keys of others without knowing those keys came from who they
claim to be from dilutes the web of trust. You do not have to sign a key
to add it to your keyring.
SPECIAL NOTE ---
If you lose your secret-key password [or forget it] or your secret-key in a
drive crash [because you failed to back it up on floppy], you cannot issue a
revocation certificate. In that case, you should make a general announcement
in all related Echos that your old key should be disabled using the PGP
disable command [PGP -kd userid] for your userid. That keeps your useless
key on their keyrings [so they won't be replaced from other lists who didn't
get the word] and permits them to add a new key from you without one
interfering with the other. BACKUP! BACKUP! BACKUP! [clear?] [grin]
This Echo is available on the Zone 1 Backbone. This Echo was Elisted
as of ELIST211. Please feel free to announce this Echo to all interested
participants in your area.
Thanks.
TTFN.
Christopher Baker & GK Pace
Moderators
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: SUPPORT the Phil Zimmerman Legal Defense Fund!
iQCVAwUBL7p4lcsQPBL4miT5AQFEWwP+IwEOLvZE5IXKYs5fLQqSFcdILPgbZxSn
xMH+XdAFBNlfrFiJJwSyrARvXF80UnURODW4V2lpaAdU4MJx8nvz35urAGGYttZ4
EG+VWu9+aI0vrO94VfLp8OfMoREjNE01s2bJJBsecboQx0y8JP0REpKmjliUQ+T6
aeLSmc5ZQIE=
=rxr0
-----END PGP SIGNATURE-----
--- GenMsg [0002] (cbak.rights@opus.global.org)
* Origin: Rights On! for Privacy! It's a Right not a privilege! (1:374/14)